Codecov Report

Attention: Patch coverage is 86.39175% with 66 lines in your changes are missing coverage. Please review.

Project coverage is 71.11%. Comparing base (8ffbf76) to head (c3f0fe6).
Report is 1 commits behind head on develop.

@@             Coverage Diff             @@
##           develop    #1976      +/-   ##
===========================================
+ Coverage    70.01%   71.11%   +1.09%     
===========================================
  Files          235      245      +10     
  Lines        13477    13643     +166     
===========================================
+ Hits          9436     9702     +266     
+ Misses        3589     3495      -94     
+ Partials       452      446       -6     

Will wait on #1961 to be merged as it will have some conflicts with the tests

!!!WARNING!!!
nosec detected in the following files: cmd/zetae2e/run.go, zetaclient/evm/evm_client.go

Be very careful about using #nosec in code. It can be a quick way to suppress security warnings and move forward with development, it should be employed with caution. Suppressing warnings with #nosec can hide potentially serious vulnerabilities. Only use #nosec when you're absolutely certain that the security issue is either a false positive or has been mitigated in another way.

Only suppress a single rule (or a specific set of rules) within a section of code, while continuing to scan for other problems. To do this, you can list the rule(s) to be suppressed within the #nosec annotation, e.g: /* #nosec G401 */ or //#nosec G201 G202 G203
Broad #nosec annotations should be avoided, as they can hide other vulnerabilities. The CI will block you from merging this PR until you remove #nosec annotations that do not target specific rules.

Pay extra attention to the way #nosec is being used in the files listed above.